Managing advisories for complex model nodes in a graphical modeling application

ABSTRACT

A system for managing advisories for complex model nodes that can include a complex model, a graphical modeling application, and an advisory manager. The complex model can be configured to graphically represent a user-defined system as multiple nodes and relationships. The graphical modeling application can be configured to execute operations upon the complex model. The graphical modeling application can store data defining the graphical characteristics of the complex model as a notation model and data defining the semantic characteristics of the complex model as a semantic model. The notation model and the semantic model can be stored as separate data entities. The advisory manager can be configured to aggregate notifications and potential resolutions for the nodes of the complex model. The notifications and potential resolutions can be visually presented within the graphical modeling application.

BACKGROUND

The present invention relates to the field of graphical modeling and,more particularly, to managing advisories for complex model nodes in agraphical modeling application.

Graphical modeling applications are effective productivity tools forsystem design tasks. The graphical modeling application allows forpieces of the system, called nodes, to be graphically represented andrelated to other nodes of the system. Additional data regarding therequirements and capabilities of a node are also entered into thegraphical modeling application to further define the node as well as thetype of relationship that the node has to other nodes.

A key function provided by conventional graphical modeling applicationsis the capability to aggregate all the advisories that affect aparticular node. For example, the advisories displayed for a networkserver can include specific notifications of its subordinate components.This aggregation of advisory information provides a user with anefficient means to access this information and examine the impact ofvarious related requirements and capabilities.

This functionality is possible because conventional graphical modelingapplications store the created model as a single entity. That is, theuser-entered data defining the graphics and semantics of the model arestored together as one model. Thus, this key functionality is lacking ingraphical modeling applications that store graphical and semantic datafor a model separately. For example, when a model is created within anECLIPSE-based modeling application, the graphics used in the model arestored as notation model and the semantic data and relationships arestored as a semantic model. As such, the approaches utilized byconventional graphical modeling applications are not applicable toECLIPSE-based graphical modeling applications.

BRIEF SUMMARY

One aspect of the present disclosure can include a system for managingadvisories for complex model nodes. Such a system can include a complexmodel, a graphical modeling application, and an advisory manager. Thecomplex model can be configured to graphically represent a user-definedsystem as multiple nodes and relationships. The graphical modelingapplication can be configured to execute operations upon the complexmodel. The graphical modeling application can store data defining thegraphical characteristics of the complex model as a notation model anddata defining the semantic characteristics of the complex model as asemantic model. The notation model and the semantic model can be storedas separate data entities. The advisory manager can be configured toaggregate notifications and potential resolutions for the nodes of thecomplex model. The notifications and potential resolutions can bevisually presented within the graphical modeling application.

Another aspect of the present disclosure can include a method formanaging advisories for complex model nodes. Such a method can determinerelated nodes for a node of a complex model. The relationship to therelated node can be captured in a notation model and a semantic modelassociated with the complex model. The complex model can be presentedwithin a graphical modeling application. An aggregate of notificationsfor the node can be created from notifications of the related nodes. Thenotifications can be generated by the graphical modeling application. Inresponse to a user-selected command, the aggregate of notifications forthe node can be presented in a distinct viewing area within thegraphical user interface of the graphical modeling application.

Yet another aspect of the present disclosure can include a computerprogram product for managing advisories for complex model nodes. Thecomputer program product can include a computer readable storage mediumhaving embedded computer usable program code. The computer usableprogram code can be configured to determine related nodes for a node ofa complex model. Relationships to related nodes can be captured in anotation model and a semantic model associated with the complex model.The complex model can be presented within a graphical modelingapplication. The computer usable program code can be configured tocreate an aggregate of notifications for the node from notifications ofthe related nodes. The notifications can be generated by the graphicalmodeling application. The computer usable program code can be configuredto present the aggregate of notifications for the node in a distinctviewing area within a graphical user interface of the graphical modelingapplication in response to a user-selected command.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a system that aggregates andpresents notifications for the nodes of a complex model within agraphical modeling application in accordance with embodiments of theinventive arrangements disclosed herein.

FIG. 2 is a flow chart of a method detailing the aggregation ofnotifications for the nodes of a complex model by an advisory manager inaccordance with an embodiment of the inventive arrangements disclosedherein.

FIG. 3 is a collection of graphical user interfaces (GUIs) illustratingthe presentation of notifications and potential resolutions within angraphical modeling application in accordance with an embodiment of theinventive arrangements disclosed herein.

DETAILED DESCRIPTION

The present disclosure details a solution for managing advisories forcomplex model nodes within a graphical modeling application. The data ofthe complex model can be stored by the graphical modeling application astwo distinct entities—a notation model and a semantic model, which is anarrangement used for an ECLIPSE-based graphical modeling application,for example. The notation model can store data pertaining to thegraphical characteristics of the complex model and the semantic modelcan store the related semantic data. An advisory manager can correlatethe data of both the notation and semantic models in order to aggregatethe notifications generated by the graphical modeling application foreach node in the complex model. The aggregated notifications can then bevisually presented within the graphical modeling application.

The present invention may be embodied as a method, system, or computerprogram product. Accordingly, the present invention may take the form ofan entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, the present invention may take the form of a computerprogram product on a computer-usable storage medium havingcomputer-usable program code embodied in the medium. In a preferredembodiment, the invention is implemented in software, which includes butis not limited to firmware, resident software, microcode, etc.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. For the purposes of this description,a computer-usable or computer readable medium can be any apparatus thatcan contain, store, communicate, propagate, or transport the program foruse by or in connection with the instruction execution system,apparatus, or device. The computer-usable medium may include apropagated data signal with the computer-usable program code embodiedtherewith, either in baseband or as part of a carrier wave. The computerusable program code may be transmitted using any appropriate medium,including but not limited to the Internet, wireline, optical fibercable, RF, etc.

Any suitable computer usable or computer readable medium may beutilized. The computer-usable or computer-readable medium may be, forexample but not limited to, an electronic, magnetic, optical,electromagnetic, infrared, or semiconductor system, apparatus, device,or propagation medium. Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory, a rigidmagnetic disk and an optical disk. Current examples of optical disksinclude compact disk-read only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD. Other computer-readable medium can include atransmission media, such as those supporting the Internet, an intranet,a personal area network (PAN), or a magnetic storage device.Transmission media can include an electrical connection having one ormore wires, an optical fiber, an optical storage device, and a definedsegment of the electromagnet spectrum through which digitally encodedcontent is wirelessly conveyed using a carrier wave.

Note that the computer-usable or computer-readable medium can eveninclude paper or another suitable medium upon which the program isprinted, as the program can be electronically captured, via, forinstance, optical scanning of the paper or other medium, then compiled,interpreted, or otherwise processed in a suitable manner, if necessary,and then stored in a computer memory.

Computer program code for carrying out operations of the presentinvention may be written in an object oriented programming language suchas Java, Smalltalk, C++ or the like. However, the computer program codefor carrying out operations of the present invention may also be writtenin conventional procedural programming languages, such as the “C”programming language or similar programming languages. The program codemay execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

A data processing system suitable for storing and/or executing programcode will include at least one processor coupled directly or indirectlyto memory elements through a system bus. The memory elements can includelocal memory employed during actual execution of the program code, bulkstorage, and cache memories which provide temporary storage of at leastsome program code in order to reduce the number of times code must beretrieved from bulk storage during execution.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening I/O controllers.

Network adapters may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

The present invention is described below with reference to flowchartillustrations and/or block diagrams of methods, apparatus (systems) andcomputer program products according to embodiments of the invention. Itwill be understood that each block of the flowchart illustrations and/orblock diagrams, and combinations of blocks in the flowchartillustrations and/or block diagrams, can be implemented by computerprogram instructions. These computer program instructions may beprovided to a processor of a general purpose computer, special purposecomputer, or other programmable data processing apparatus to produce amachine, such that the instructions, which execute via the processor ofthe computer or other programmable data processing apparatus, createmeans for implementing the functions/acts specified in the flowchartand/or block diagram block or blocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer orother programmable data processing apparatus to cause a series ofoperational steps to be performed on the computer or other programmableapparatus to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide steps for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

FIG. 1 is a schematic diagram illustrating a system 100 that aggregatesand presents notifications for the nodes 135 of a complex model 130within a graphical modeling application 115 in accordance withembodiments of the inventive arrangements disclosed herein. In system100, a user 105 can view notifications aggregated by an advisory manager155 within the user interface 120 of a graphical modeling application115 operating on a client device 1 10. In one embodiment, theapplication 115 can be an ECLIPSE-based graphical modeling applicationor any other modeling application that represents a complex model as anotational model and a semantic model, which are digitally encoded in astorage medium a manner distinct from each another.

The client device 110 can represent a variety of electronic computingdevices capable of running the graphical modeling application 115. Thegraphical modeling application 115 can represent a software applicationcapable of performing a variety of functions for thecreation/modification of a complex model 130. In an ECLIPSE embodiment,for example, the graphical modeling application 115 can utilize theECLIPSE Modeling Framework (EMF) and/or the Graphical Editing Framework(GEF).

As used herein, the term “complex model” is used to describe a modelconsisting of multiple data models. That is, the unified display of thecomplex model 130 within the graphical modeling application 115 isproduced through the correlation of the notation model 145 and semanticmodel 140.

The complex model 130 can consist of multiple related nodes 135. Datapertaining to the graphical representation of the nodes 135 can bestored in a data store 150 by the graphical modeling application 115 asa notation model 145, such as the shape of the nodes and the edges orlines that connect them. Semantic data, such as capability andrequirements parameters, entered by the user 105 to define nodes 135 andtheir relationships can be stored as a semantic model 140 within thedata store 150.

It is important to note that a node 135 of the complex model 130 cancontain or relate to another complex model 130. Therefore, by extension,a complex model 130 can consist of multiple notation models 145 and/orsemantic models 140.

The graphical modeling application 115 can include a user interface 120and an advisory manager 155. The advisory manager 155 can represent asoftware component of the graphical modeling application 115 configuredto handle presentation of various advisories, such as notifications andresolutions, that pertain to a user-specified node 135 within anadvisory details display 125.

The advisory manager 155 can include a notification handler 160, aresolution handler 165, an interface handler 170, and notificationprocessing rules 175. The notification handler 160 can represent thecomponent of the advisory manager 155 configured to aggregatenotifications generated by the graphical modeling application 115 foreach node 135 of the complex model 130.

A notification can represent an item of data indicating a problem orpotential problem with the complex model 130 in its current state thatcan be identified by the graphical modeling application 115 based on ananalysis of the complex model 130. Examples of notifications caninclude, but are not limited to, a warning, an unsatisfied requirementor capability, an unsatisfied optional requirement or capability, anincompatibility notice, and the like.

It should be noted that the types of notifications handled by thenotification handler 160 may be dependent on those supported by thegraphical modeling application 115. That is, the notification handler160 may be able to only aggregate the types of notifications that aregenerated by the specific graphical modeling application 115.

Aggregation of notifications by the notification handler 160 can beinfluenced by a set of notification processing rules 175. Thenotification processing rules 175 can represent guidelines by which thenotification handler 160 determines which notifications from relatednodes 135 to include for the present node 135 and if any characteristicsof the notification require adjustment. The notification processingrules 175 can also include user-configurable parameters and/oruser-defined rules.

For example, a notification processing rule 175 can dictate that anunsatisfied optional requirement from a subordinate node 135 should notbe included in the aggregate of notifications for its superior node 135.

Once the notifications for a node 135 have been aggregated, theresolution handler 165 can determine a set of potential resolutions forthe notifications. Potential resolutions identified by the resolutionhandler 165 can be generated by an internal algorithm or provided by acomparable component of the graphical modeling application 115.

It is important to note that the set of potential resolutions determinedby the resolution handler 165 encompasses resolutions for the aggregateof notifications for the node 135. That is, the set of potentialresolutions can include resolutions that address notifications forrelated nodes 135 that affect the present node 135.

Communications between the advisory manager 155 and the graphicalmodeling application 115 can be overseen by the interface handler 170.The interface handler 170 can be configured to utilize standardizedcommunication protocols and/or application programming interface (API)commands to manage the data exchanges necessary for the function of thenotification handler 160 and/or resolution handler 165.

The interface handler 170 can be responsible for presenting the advisorydetails display 125 within the user interface 120 of the graphicalmodeling application 115 in response to a user-selected command. Theadvisory details display 125 can represent a distinct viewing area ofthe user interface 120 in which the aggregated notifications and set ofpotential resolutions can be presented for a user-selected node 135.

In an alternate embodiment, the advisory manager 155 can be a separatesoftware component capable of interacting with the graphical modelingapplication 115 to perform the previously-described functionality. Forexample, in an ECLIPSE-based embodiment, the advisory manager 155 can bean ECLIPSE plug-in designed to provide advisory management to anexisting ECLIPSE-based graphical modeling application.

As used herein, presented data store 150 can be a physical or virtualstorage space configured to store digital information. Data store 150can be physically implemented within any type of hardware including, butnot limited to, a magnetic disk, an optical disk, a semiconductormemory, a digitally encoded plastic memory, a holographic memory, or anyother recording medium. Data store 150 can be a stand-alone storage unitas well as a storage unit formed from a plurality of physical devices.Additionally, information can be stored within data store 150 in avariety of manners. For example, information can be stored within adatabase structure or can be stored within one or more files of a filestorage system, where each file may or may not be indexed forinformation searching purposes. Further, data store 150 can utilize oneor more encryption mechanisms to protect stored information fromunauthorized access.

FIG. 2 is a flow chart of a method 200 detailing the aggregation ofnotifications for the nodes of a complex model by an advisory manager inaccordance with an embodiment of the inventive arrangements disclosedherein. Method 200 can be performed in the context of system 100 or anyother system in which a graphical modeling application segregates thedata of a complex model into a notation model and a semantic model.

Method 200 can begin with step 205 where the advisory manager can accessthe notation and semantic models of the complex model presented withinthe graphical modeling application. In step 210, a starting node can beselected to be processes as the node under examination. A set of relatednodes for the node under examination can be determined in step 215.

In step 220, it can be determined if the related nodes havenotifications. When the related nodes do not have notifications for thenode under examination, step 260 can execute where it can be determinedif there are more nodes of the complex model to process.

When more nodes of the complex model require processing, the next nodeof the complex model can be set as the node under examination in step265 and flow of method 200 can return to step 215 to continueprocessing. When no other nodes of the complex model require processing,step 270 can execute where the aggregation of notifications for thecomplex model is completed.

When it is determined in step 220 that the related nodes havenotifications, the semantic relationships between a related node and thenode under examination can be analyzed in step 225. In step 230, it canbe determined if the notification for the related node should beincluded for the node under examination.

When the notification is not to be included with the node underexamination, step 250 can execute where it can be determined if thereare more related nodes to examine. When there are no other related nodesto be examined for the node under examination, flow of method 200 canproceed to step 260 to determine the continuation or termination of theaggregation process.

When there are more related nodes to examine, the next related node canbe examined in step 255. From step 255, flow can return to step 225 tocontinue examination of the related nodes for the node underexamination.

When it is determined in step 230 that the notification is not beincluded for the node under examination, step 235 can execute where itcan be determined if a change to an advisory characteristic of thenotification is necessary. For example, processing of an unsatisfiedcapability can determine that it should be changed to an optionalcapability for the node under examination.

When it is determined that a change in an advisory characteristic isrequired, the advisory characteristic of the notification can bemodified for the node under examination in step 240. After execution ofstep 240, or when a change in an advisory characteristic is notrequired, step 245 can execute where the notification is added to theaggregate of notifications for the node under examination.

From step 245, flow of method 200 can proceed to step 250 to determinethe existence of additional related nodes to process and thecontinuation of the notification aggregation process.

FIG. 3 is a collection 300 of graphical user interfaces (GUIs) 305 and340 illustrating the presentation of notifications and potentialresolutions within a graphical modeling application in accordance withembodiments of the inventive arrangements disclosed herein. The GUIs ofcollection 300 can be utilized within the context of system 100 and/orthe execution of method 200.

It should be noted that the GUIs of collection 300 are for illustrativepurposes only, and are not intended to represent comprehensiveembodiments. As such, variation in representation and/or configurationscan be made without deviating from the spirit of the present disclosure.

The graphical modeling application user interface 305 can allow a userto perform a variety of operations upon a complex model 315 presentedwithin the modeling workspace 310. To highlight the interaction of anembodiment of the invention, a selected node 320 of the complex model315 has been enlarged for discussion purposes.

As shown in this example, the selected node 320 is graphicallyrepresented as a rectangular container labeled “MidWest Offices”. Theselected node 320 also has a “one-to-one” relationship with the nodelabeled “HQ”. The node components 325 of the selected node 320 can alsobe displayed in its graphical representation within the ECLIPSE-basedgraphical modeling application user interface 305.

Additionally, the graphical representation of the selected node 320 andits node components 325 can include advisory indicators 330 and anadvisory details launch mechanism 335. An advisory indicator 330 can bea graphic that visually signifies the existence of and/or the severityof the advisories for the selected node 320 and/or node components 325.The advisory indicators 330 can be related to the notificationprocessing performed by the advisory manager.

The advisory details launch mechanism 335 can represent the means bywhich a user can access the advisory details display 340 for theselected node 320. The advisory details launch mechanism 335 can includea visual indicator within the graphical representation of the selectednode 320.

As shown in this example, the advisory details launch mechanism 335 canbe a button displayed in the selected node 320 that can be selected bythe user with an interaction mechanism 338. Multiple advisory detailslaunch mechanisms 335 can be made available within the graphicalmodeling application user interface 305, such as a selectable menucommand in addition to a graphical button.

Selection of the advisory details launch mechanism 335 can present theadvisory details display 340 for the selected node 320 within thegraphical modeling application user interface 305. The advisory detailsdisplay 340 can present the user with detailed information regarding theadvisories associated with the selected node 320.

The advisory details display 340 can include a text search area 345,display filters 350, a notifications area 355, and a resolutions area360. The notifications area 355 can display the aggregated notificationsfor the selected node 320. Since notifications for the selected node 320are aggregated from related nodes in the complex model 315, thenotifications area 355 can include pertinent notifications from nodecomponents 325.

The origin of the notifications can be preserved and displayed in thenotifications area 355, as shown by the hierarchical tree structurepresentation. Additionally, the advisory indicator 330 of eachnotification can also be displayed within the notifications area 355.

A user can utilize the text search area 345 to search for occurrences ofa specific word or phrase within the notifications presented within thenotifications area 355. Additional refinement of the notificationsdisplayed within the notifications area 355 can be provided by thedisplay filters 350. Selection of a specific display filter 350 canlimit the contents of the notifications area 355 to only thosenotifications having the corresponding characteristic, such as advisoryindicator 330.

The resolutions area 360 can present potential resolutions to thenotifications of the notifications area 355, as determined by theadvisory manager. A resolution execution mechanism 365 can be includedfor each presented resolution in the resolutions area 360.

Selection of a resolution execution mechanism 365 can initiate a set ofprogrammatic commands executed by the advisory manager and/or thegraphical modeling application to perform the resolution. The changescaused by the execution of a resolution can result in a change ofinformation presented within the advisory details display 340.

For example, selection of the resolution “Set ‘NewServer’ state toINSTALLED” can trigger a series of operations that resolve allnotifications for the selected node 320. Thus, the advisory detailsdisplay 340 would change to inform the user that there are no advisoriesfor the selected node 320.

It should be noted, however, that the execution of multiple resolutionsmay be necessary to resolve all notifications for the selected node 320.Further, situations may exist for which the advisory manager is unableto determine an automated solution. In such an event, the resolutionsarea 360 can include a manual resolution option (not shown).

The diagrams in FIGS. 1-3 illustrate the architecture, functionality,and operation of possible implementations of systems, methods, andcomputer program products according to various embodiments of thepresent invention. In this regard, each block in the flowchart or blockdiagrams may represent a module, segment, or portion of code, whichcomprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that, in somealternative implementations, the functions noted in the block may occurout of the order noted in the figures. For example, two blocks shown insuccession may, in fact, be executed substantially concurrently, or theblocks may sometimes be executed in the reverse order, depending uponthe functionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts, or combinations of special purpose hardware andcomputer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A system for managing advisories for complex model nodes comprising:a complex model configured to graphically represent a user-definedsystem as a plurality of nodes and relationships; a graphical modelingapplication configured to support execution of a plurality of operationsupon the complex model, wherein said graphical modeling applicationstores data defining graphical characteristics of the complex model as anotation model and stores data defining semantic characteristics of thecomplex model as a semantic model, wherein the notation model and thesemantic model are stored in a storage medium as separate data entities;and an advisory manager configured to aggregate notifications andpotential resolutions for the plurality of nodes of the complex model,wherein said notifications and potential resolutions are visuallypresented within the graphical modeling application.
 2. The system ofclaim 1, wherein the graphical modeling application and advisory managerutilize at least one of an ECLIPSE Modeling Framework (EMF) and aGraphical Editing Framework (GEF).
 3. The system of claim 1, wherein theadvisory manager further comprises: a notification handler configured tocorrelate and analyze the notation model and the semantic modelassociated with the complex model to identify and aggregate thenotifications for each node of the complex model, wherein an aggregateof notifications for a node encompasses notifications forsemantically-related nodes; a resolution handler configured to determinethe potential resolutions to the notifications identified by thenotification handler; a plurality of processing rules definingoperational guidelines for the at least one of the notification handlerand the resolution handler; and an interface handler configured tomanage interactions between the graphical modeling application, thenotification handler, and the resolution handler.
 4. The system of claim3, wherein the interactions managed by the interface handler comprise atleast one of a presentation of notifications, a presentation ofpotential resolutions, and an execution of a potential resolution. 5.The system of claim 4, wherein the execution of the potential resolutionmodifies at least one of the notation model and the semantic modelassociated with the complex model.
 6. The system of claim 3, wherein theplurality of processing rules comprises a set of at least oneuser-configurable parameter.
 7. The system of claim 1, wherein anotification for a node comprises at least one of a warning, anunsatisfied requirement, an optional requirement, an unsatisfiedcapability, an optional capability, and an incompatibility notice. 8.The system of claim 1, wherein the advisory manager is an integratedcomponent of the graphical modeling application.
 9. A method formanaging advisories for complex model nodes comprising: determining atleast one related node for a node of a complex model, wherein arelationship to the at least one related node is captured in a notationmodel and a semantic model associated with the complex model, and,wherein the complex model is presented within a graphical modelingapplication; creating an aggregate of notifications for the node fromnotifications of the at least one determined related node, wherein saidnotifications are generated by the graphical modeling application; andin response to a user-selected command, presenting said aggregate ofnotifications for the node in a distinct viewing area within a graphicaluser interface of the graphical modeling application.
 10. The method ofclaim 9, wherein said notifications comprise at least one of a warning,an unsatisfied requirement, an optional requirement, an unsatisfiedcapability, an optional capability, and an incompatibility notice. 11.The method of claim 9, wherein the aggregating of the notificationsfurther comprises: locating the node within the notation model and thesemantic model; correlating a relationship of the node within thenotation model with corresponding semantic data of the semantic modelfor the at least one related node; identifying an existence ofnotifications associated with the at least one related node; anddetermining an inclusion of a notification from the at least one relatednode within the aggregate of notifications for the node.
 12. The methodof claim 11, wherein determining the inclusion of the notificationfurther comprises: assessing an advisory type of the notification forthe at least one related node; analyzing the semantic data of therelationship between the node and the at least one related node withrespect to the assessed advisory type; and based said analysis,adjusting the advisory type of the notification within the aggregate ofnotifications.
 13. The method of claim 12, wherein the analysis of thesemantic data utilizes a plurality of predetermined processing rules.14. The method of claim 9, further comprising: determining at least onepotential resolution for the aggregate of notifications for the node;and presenting the at least one potential resolution within the distinctviewing area coupled with the aggregate of notifications, wherein saidpresented at least one potential resolution is coupled with auser-selectable initiation mechanism to execute the at least onepotential resolution.
 15. The method of claim 14, wherein execution of apotential resolution modifies at least one of the notation model and thesemantic model associated with the complex model.
 16. A computer programproduct for managing advisories for complex model nodes comprising acomputer readable storage medium having computer usable program codeembodied therewith, the computer usable program code comprising:computer usable program code configured to determine at least onerelated node for a node of a complex model, wherein a relationship tothe at least one related node is captured in a notation model and asemantic model associated with the complex model, and, wherein thecomplex model is presented within a graphical modeling application;computer usable program code configured to create an aggregate ofnotifications for the node from notifications of the at least onedetermined related node, wherein said notifications are generated by thegraphical modeling application; and computer usable program codeconfigured to present said aggregate of notifications for the node in adistinct viewing area within a graphical user interface of the graphicalmodeling application in response to a user-selected command.
 17. Thecomputer program product of claim 16, wherein the aggregating of thenotifications further comprises: computer usable program code configuredto locate the node within the notation model and the semantic model;computer usable program code configured to correlate a relationship ofthe node within the notation model with corresponding semantic data ofthe semantic model for the at least one related node; computer usableprogram code configured to identify an existence of notificationsassociated with the at least one related node; and computer usableprogram code configured to determine an inclusion of a notification fromthe at least one related node within the aggregate of notifications forthe node.
 18. The computer program product of claim 17, whereindetermining the inclusion of the notification further comprises:computer usable program code configured to assess an advisory type ofthe notification for the at least one related node; computer usableprogram code configured to analyze the semantic data of the relationshipbetween the node and the at least one related node with respect to theassessed advisory type; and computer usable program code configured toadjust the advisory type of the notification within the aggregate ofnotifications based said analysis.
 19. The computer program product ofclaim 16, further comprising: computer usable program code configured todetermine at least one potential resolution for the aggregate ofnotifications for the node; and computer usable program code configuredto present the at least one potential resolution within the distinctviewing area coupled with the aggregate of notifications.
 20. Thecomputer program product of claim 16, wherein the computer programproduct utilizes at least one of an ECLIPSE Modeling Framework (EMF) anda Graphical Editing Framework (GEF).